Repository navigation
Rescue: keep reconnecting until the reset goes out - #106
Merged
Merged
Conversation
A wedged Watch 3 Pro is reachable only now and then: a stuck watch in the field stayed connectable for seconds, the emulator's boot loop for a fraction of one. The rescue page now picks the watch once and keeps reconnecting to it (no picker) until the factory reset is sent or the user presses Stop; a closed picker still ends it. It also warns when the browser holds no auth key, since pairing needs a tap the stuck watch can't take. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CQSU8M5ytC26gZ1F3vdZ7B
…than a reset The rescue page can now delete every face this browser flashed (the upload handshake with new_wf_id 0, a minimal face as filler) instead of wiping the watch; it retries like the reset does. Unconfirmed on a stuck watch, so the factory reset stays next to it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CQSU8M5ytC26gZ1F3vdZ7B
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Watch 3 Pro owners stuck after a heavy face (see #104) try
/rescue, but it makes one attempt: pick, connect, reset. A wedged watch is reachable only now and then. A real stuck watch stayed listed in Chrome's picker for ~27 s and took 4.1 s to connect plus 0.9 s for service discovery. In the cmf-watch-utils emulator, the boot loop keeps Bluetooth up for only ~0.1–0.3 s before each crash.What
rescue.model: after the one pick, it keeps reconnecting to the same watch throughWatch.connect({ rescue: true, again: true }), with no picker, every 300 ms until the factory reset goes out. Stop ends the loop without an error. Closing the picker is not retried.ble.ts:connect({ again })reuses the picked device;hasSavedKey()./rescuewarns when this browser holds no auth key. Without one, connecting means pairing, which needs a tap the stuck watch can't take. The new strings are in all five languages.Verification
tests/rescue-retry.browser.test.ts: two drops then a reset on the third try, picked once; Stop; a closed picker. The unit tests (22 files) and the browser tests (55 files) pass.check,lintandformatare clean.🤖 Generated with Claude Code
https://claude.ai/code/session_01CQSU8M5ytC26gZ1F3vdZ7B